Pairing a computing device to a user

ABSTRACT

A method for automatically pairing an input device to a user is provided herein. According to one embodiment, the method includes receiving an input from an unpaired input device within an observed scene, and calculating a position of the unpaired input device upon receiving the input. The method further includes detecting one or more users within the observed scene via a capture device, creating a candidate list of the one or more detected users determined to be within a vicinity of the unpaired input device, and assigning one detected user on the candidate list to the unpaired input device to initiate pairing.

BACKGROUND

Computing devices are becoming increasingly more interactive. Further,various different computing devices may be communicatively linked so asto provide an enhanced computing experience for each user. For example,a user may provide input via a wireless device to control aspects of agaming computing device. Such a wireless device may be utilized byvarious different users, and such users may desire to identifythemselves upon taking control of the wireless device. One priorapproach prompts a user to enter a user name and/or passphrase to gainaccess to the gaming computing device. However, such an approachinterrupts gameplay, which detracts from the gaming experience andcauses user frustration.

SUMMARY

A method for automatically pairing an input device to a user is providedherein. According to one embodiment, the method includes receiving aninput from an unpaired input device within an observed scene, andcalculating a position of the unpaired input device upon receiving theinput. The method further includes detecting one or more users withinthe observed scene via a capture device, creating a candidate list ofthe one or more detected users determined to be within a vicinity of theunpaired input device, and assigning one detected user on the candidatelist to the unpaired input device to initiate pairing.

This Summary is provided to introduce a selection of concepts in asimplified form that are further described below in the DetailedDescription. This Summary is not intended to identify key features oressential features of the claimed subject matter, nor is it intended tobe used to limit the scope of the claimed subject matter. Furthermore,the claimed subject matter is not limited to implementations that solveany or all disadvantages noted in any part of this disclosure.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 schematically shows an example computing environment including anexample mobile device according to an embodiment of the presentdisclosure.

FIG. 2 is a flowchart that illustrates an example method for pairing themobile device of FIG. 1 to a user according to an embodiment of thepresent disclosure.

FIG. 3 is a flowchart that illustrates an example method for terminatingthe pairing of the mobile device of FIG. 1 to the user according to anembodiment of the present disclosure.

FIG. 4 is a flowchart that illustrates an example method fortransferring the pairing of the mobile device of FIG. 1 to another useraccording to an embodiment of the present disclosure.

FIG. 5 is a schematic view of a computing system that may be used as thegaming system of FIG. 1.

DETAILED DESCRIPTION

Aspects of this disclosure will now be described by example and withreference to the illustrated embodiments listed above.

FIG. 1 shows an example 3D interaction space 100 in which user 10 islocated. FIG. 1 also shows gaming system 12 which may enable user 10 tointeract with a video game. Gaming system 12 may be used to play avariety of different games, play one or more different media types,and/or control or manipulate non-game applications and/or operatingsystems. Gaming system 12 may include gaming console 14 and displaydevice 16, which may be used to present game visuals to game players.Gaming system 12 is a type of computing device, the details of whichwill be discussed with respect to FIG. 6.

Turning back to FIG. 1, 3D interaction space 100 may also include acapture device 18 such as a camera, which may be coupled to gamingsystem 12. Capture device 18, for example, may be a depth camera used toobserve 3D interaction space 100 by capturing images. Thus, 3Dinteraction space may also be referred to herein as an observed scene.As such, capture device 18 may be used to capture images of user 10which may be used to identify user 10. For example, user 10 may beidentified by a physical attribute unique to user 10 by employingthree-dimensional imaging, facial recognition, biometrics, or anotheruser identifying technology. Further, in some embodiments, a presence ofuser 10 may be detected without determining an identity of the user.

As shown, user 10 is holding an input device 20 with right hand 22. User10 may interact with input device 20 to control aspects of gaming system12. In the depicted example, input device 20 is a magic wand which maybe used to cast spells in a wizard game, for example. Because a positionof input device 20 is within a vicinity of right hand 22, input device20 may be automatically paired to user 10. For example, capture device18 and/or another sensor of computing system 12 may determine a positionof input device 20 and a position of user 10. Further, computing system12 may determine that user 10 is a nearest user to input device 20. Asdescribed in more detail below, the nearest user to an input device maybe automatically paired to the input device.

FIG. 1 further shows a second user 24 and a third user 26. The secondand third users may also be present within 3D interaction space 100,thus, the second and third users may also be observed by capture device18. As shown, second and third users are farther from input device 20than user 10. Therefore, the second user and the third user may be at aposition that is not within the vicinity of input device 20. As such,neither user 24 nor user 26 may be paired to input device 20.

FIG. 1 further shows various unpaired computing devices, such ascontroller 28 and mobile computing device 30. Such devices may beunpaired because the devices are idle. In other words, neither user 10,user 24, nor user 26 is interacting with controller 28 or mobilecomputing device 30; therefore, computing system 12 is not receivinginput from either device. As such, controller 28 and mobile device 30may be in an unpaired state. However, such devices may be automaticallypaired to a user when computing system 12 receives input from anunpaired device. For example, user 24 may pick up controller 28 andpress a button to block the casted spell, and computing system 12 mayautomatically pair controller 28 to user 24 upon receiving the input ofthe pressed button.

It will be appreciated that FIG. 1 is provided by way of example, andthus, is not meant to be limiting. Therefore, it is to be understoodthat a wizard game is provided to illustrate a general concept, andvarious other games and non-game applications are possible withoutdeparting from the scope of this disclosure.

Further, it will be appreciated that a user may interact with the inputdevice in any suitable way. Therefore, it is to be understood that user10 interacting with the input device using right hand 22 is provided byway of example, and thus, is not meant to be limiting. For example, user10 may interact with an input device using a left hand. As anotherexample, the input device may be attached to a body portion of user 10,such as a leg, a knee, a shoulder, an elbow, or another body portion. Inthis way, the user may interact with an input device attached to theuser's body, and a position of such an input device may be determinedand associated with a particular body portion to which the input deviceis attached. For example, the computing system may determine that theattached input device and the associated body portion are co-localized,and thus may be moving similarly. As such, the computing system maydetermine that the user is interacting with the attached input device.Continuing with the above example, user 10 may attach a shield inputdevice to a forearm and such an attached input device may be used toshield a casted spell, for example.

FIG. 2 is a flowchart that illustrates an example method 200 forautomatically pairing an input device to a user. Method 200 may beexecuted by a main computing device (e.g., gaming system 12)communicatively coupled to the input device (e.g., input device 20), forexample.

At 202, method 200 includes receiving an input from an unpaired inputdevice within an observed scene. For example, the received input mayinclude a button press, a joystick movement, a D-pad movement, a touchevent, and/or a detected motion of the unpaired input device. Further,the unpaired input device may include a motion sensor and/or a tag thatmay indicate the detected motion of the device. For example, the motionsensor may provide the detected motion input to the main computingdevice. As another example, a capture device of the main computingdevice may detect the detected motion of the tag associated with theunpaired input device. It will be appreciated that the unpaired inputdevice emits a wireless signal that is received by the computing maindevice, and which contains an input device identifier by which thecomputing device may identify the input device. The input device 20itself may be a game controller, mobile telephone, tablet computer, orother device capable of communicating with the computing device by awireless signal. The wireless signal may be in the form of infrared,BLUETOOTH, WiFi, or other suitable wireless signal. Further, the inputdevice identifier may be a GUID, MAC address, or other identifier thatis used to distinguish the input device from other input devices in thescene.

At 204, method 200 includes calculating a position of the unpaired inputdevice upon receiving the input. For example, the position may include adistance and an angle of the unpaired input device from the maincomputing device. In some embodiments, calculating the position mayinclude a beamforming technique to determine the distance and the angleof the unpaired input device with respect to the main computing device.However, it will be appreciate that other techniques are possiblewithout departing from the scope of this disclosure. For example, atwo-dimensional positioning technique may be used. As another example, athree-dimensional positioning technique may be used. Further, in someembodiments the unpaired input device may include a tag and the positionof the unpaired input device may be determined by locating a position ofthe tag. For example, the tag may include visible identifyinginformation which may be detected by the main computing device. Thus, itwill be appreciated that the tag may be an augmented reality marker thatcontains an optical code that is captured in an image taken by a camera,such as a visible light camera, which is associated with the maincomputing device, and the position of the marker in the scene can bedetermined by the main computing device.

At 206, method 200 includes detecting one or more users within theobserved scene via a capture device of the main computing device,wherein the observed scene includes the unpaired input device. Forexample, capture device 18 may detect one or more users within theobserved scene.

At 208, method 200 includes creating a candidate list of the one or moredetected users determined to be within a vicinity of the unpairedcomputing device. For example, the candidate list may include user 10,user 24, and user 26 of FIG. 1. Further, the candidate list may includea distance between each user and the unpaired input device for which theinput was received. Further, the candidate list may include a right handdistance, a left hand distance, and a geometric center distance of eachuser as measured with respect to the position of the unpaired inputdevice. Further, such a candidate list may be sorted by proximity to theunpaired input device with respect to each distance.

It will be appreciated that the candidate list may be created in anysuitable way. For example, the candidate list may be sorted by distancein ascending or descending order. As another example, one or moredetected users may be excluded from the candidate list if such usersexceed a threshold distance from the unpaired input device. In this way,those users which are too far away from the unpaired input device to bea conceivable candidate for pairing may be automatically removed fromthe candidate list to reduce processing time, for example.

At 210, method 200 includes assigning one detected user on the candidatelist to the unpaired input device to initiate pairing, the one userbeing a nearest user to the unpaired computing device. Further, onceassigned, the unpaired input device may be considered a paired inputdevice. In some embodiments, the nearest user is a user on the candidatelist with a strongest correlation to the unpaired input device. Forexample, the right hand distance, the left hand distance, and/or thegeometric center distance of the nearest user may be the smallestdistance from the input device included on the candidate list. In thisway, the nearest user may be automatically paired to the unpaired inputdevice. Further, assigning the nearest user to the unpaired input devicemay include automatically pairing a profile associated with the nearestuser to the input device.

At 212, method 200 includes tracking the nearest user and the pairedinput device. For example, tracking the nearest user and the pairedinput device may include correlating a motion of the right hand, theleft hand, and/or the geometric center of the nearest user to the motionof the paired computing device. For example, a motion of the user'sright hand may provide input through interaction with an input device.In the example provided above, user 10 waves magic wand 20 to provideinput to gaming system 12. The concurrent motion of the right hand ofuser 10 and magic wand 20 may be tracked using depth camera 18, forexample. Since the motion of the right hand and the motion of the magicwand occur concurrently, the gaming system may determine that user 10remains paired with magic wand 20.

It will be appreciated that method 200 is provided by way of example,and thus, is not meant to be limiting. Therefore, it is to be understoodthat method 200 may include additional and/or alternative steps thanthose illustrated in FIG. 2. For example, in some embodiments, a nearestuser may interact with two different devices to provide input to acomputing device via the two different devices. In such a scenario, bothdevices may be paired to the nearest user concurrently.

Further, it is to be understood that method 200 may be performed in anysuitable order. Further still, it is to be understood that one or moresteps may be omitted from method 200 without departing from the scope ofthis disclosure.

For example, method 200 may further include identifying each detecteduser within the observed scene by identifying a physical attribute ofeach detected user and matching the physical attribute of each detecteduser to a profile associated with each detected user. As non-limitingexamples, the physical attribute may be detected using three-dimensionalimaging, facial recognition, biometric based detection and/or other useridentifying technologies. In this way, the detected user may beidentified and paired to the input device such that the profile of thedetected user is associated with the paired input device.

FIG. 3 is a flowchart that illustrates an example method 300 forterminating the pairing of an input device to a user. At 302, method 300includes paring an input device to a nearest user. For example, method200 may be used to pair the input device to the nearest user.

At 304, method 300 includes determining if input from the input deviceis received by a computing device. If the answer to 304 is YES, method300 proceeds to 306. If the answer to 304 is NO, method 300 proceeds to308.

At 306, method 300 includes continuing to pair the input device to thenearest user. For example, if the nearest user is interacting with theinput device, then the nearest user may continue to be paired to theinput device.

At 308, method 300 includes determining if input from the input deviceis received by the computing device within a threshold period of time.For example, the input device may be temporarily idle. As such, thenearest user may not be actively interacting with the input device at aparticular moment in time. For example, the nearest user may interactwith the input device to cast a spell, and the input device may betemporarily idle immediately after casting the spell. For example, thenearest user may be waiting for another game player to cast an opposingspell. It will be appreciated that the threshold period of time may beany suitable period of time. Further, the threshold period of time mayvary for different settings, different games, and/or different non-gameapplications. As such, the threshold period of time may be customizableby a user and/or by a game/application developer. If the answer to 308is NO, method 300 continues to 310. If the answer to 308 is YES, method300 continues to 312.

At 310, method 300 includes terminating an association of the nearestuser to the input device. For example, the input device may be idlebecause the nearest user set the input device down and/or decided to enda gaming session. Since the user does not interact with the input devicewithin the threshold period of time, the input device may be unpairedfrom the nearest user, for example. As another example, the nearest usermay hand off the input device to another user, and therefore the nearestuser may be a former nearest user. Such an example of transferring apaired input device from one user to another user is described infurther detail below with respect to FIG. 4.

At 312, method 300 includes comparing a position of the input device toa position of the nearest user. For example, the position of the inputdevice may be compared to a position of a right hand of the nearestuser.

At 314, method 300 includes determining if the position of the inputdevice is within a vicinity of the position of the nearest user. Forexample, the vicinity may be a threshold distance from the input device.As one non-limiting example, the threshold distance may be a twelve inchradius around a perimeter of the paired input device. However, it willbe appreciated that other threshold distances are possible withoutdeparting from the scope of this disclosure. Further, if the nearestuser is within the threshold distance, then the user may be within thevicinity of the input device. If the answer to 314 is NO, method 300continues to 310 and an association of the nearest user to the inputdevice is terminated. If the answer to 314 is YES, method 300 continuesto 316.

At 316, method 300 includes continuing paring the input device to thenearest user. For example, the input device may be idle yet the user maystill be holding the input device. Therefore, the nearest user may stillbe within the vicinity of the input device. Further, the nearest usermay be providing periodic input via interaction with the input device;however, the periodic input may be provided within the threshold periodof time. Thus, the nearest user may remain paired with the input device.

It will be appreciated that method 300 is provided by way of example,and thus, is not meant to be limiting. Therefore, it is to be understoodthat method 300 may include additional and/or alternative steps thanthose illustrated in FIG. 3. Further, it is to be understood that method300 may be performed in any suitable order. Further still, it is to beunderstood that one or more steps may be omitted from method 300 withoutdeparting from the scope of this disclosure.

FIG. 4 is a flowchart that illustrates an example method 400 fortransferring the pairing of an input device to another user. At 402,method 400 includes tracking a first user and a paired input device,wherein the first user is a nearest user.

At 404, method 400 includes determining if a position of the first useris within a vicinity of the paired input device. For example, thevicinity may be a threshold distance from the paired input device, asdescribed above. If the answer to 404 is YES, method 400 continues to406. If the answer to 404 is NO, method 400 continues to 408.

At 406, method 400 includes continuing to track a position of the firstuser and the paired input device. As such, the first user may remainwithin the vicinity of the paired input device. Therefore, the firstuser may continue to interact with the input device to control aspectsof a video game, for example.

At 408, method 400 includes determining if a position of a second useris within the vicinity of the paired input device. If the answer to 408is NO, method 400 continues to 410. If the answer to 408 is YES, method400 continues to 412.

At 410, method 400 includes terminating an association of the first userto the paired input device. For example, the first user may ‘hand off’the paired input device to the second user. Therefore, in such ascenario the first user may be a former nearest user, and thus the firstuser may be unpaired from the input device.

At 412, method 400 includes transferring the paired input device to thesecond user. As such, an association between the second user and thepaired input device may be formed. Therefore, in such a scenario, thesecond user may be a current nearest user to the input device. Asdescribed above, second user may receive the input device from the firstuser as a hand off. Further, it will be appreciated that the second userand the paired input device may be tracked, as described above.

It will be appreciated that method 400 is provided by way of example,and thus, is not meant to be limiting. Therefore, it is to be understoodthat method 400 may include additional and/or alternative steps thanthose illustrated in FIG. 4. Further, it is to be understood that method400 may be performed in any suitable order. Further still, it is to beunderstood that one or more steps may be omitted from method 200 withoutdeparting from the scope of this disclosure.

As described above, by pairing an input device to a user based on aposition of the input device and a position of the user, the user can beautomatically paired to the input device. In this way, the user canavoid having to log into a user account or having to perform othermanual inputs to pair a device. Further, by automatically pairing thedevice to the user in this way, the user may pick up a new device,switch devices with another user, use more than one device, etc. and theone or more devices may be paired to the user automatically inreal-time. As such, the gaming experience may be enhanced. For example,using the above example, the user may interact with the wand inputdevice to cast a spell, and the user may switch to interact with thecontroller to throw a punch or another physical attack. As such, thegaming experience may be enhanced by allowing the user to interact withdifferent input devices which may allow different gaming controls, whileswitching the pairing of the user between the different input devicesautomatically. In this way, the gaming experience may be enhanced.

In some embodiments, the above described methods and processes may betied to a computing system including one or more computers. Inparticular, the methods and processes described herein may beimplemented as a computer application, computer service, computer API,computer library, and/or other computer program product.

FIG. 5 schematically shows a non-limiting computing system 70 that mayperform one or more of the above described methods and processes.Computing system 70 is shown in simplified form. It is to be understoodthat virtually any computer architecture may be used without departingfrom the scope of this disclosure. In different embodiments, computingsystem 70 may take the form of a mainframe computer, server computer,desktop computer, laptop computer, tablet computer, home entertainmentcomputer, network computing device, mobile computing device, mobilecommunication device, gaming device, etc.

Computing system 70 includes a processor 72 and a memory 74. Computingsystem 70 may optionally include a display subsystem 76, communicationsubsystem 78, sensor subsystem 80 and/or other components not shown inFIG. 5. Computing system 70 may also optionally include various userinput devices such as keyboards, mice, game controllers, cameras,microphones, and/or touch screens, for example. FIG. 6 shows a gamecontroller 28, magic wand 20, and a mobile computing device 30, whichmay provide input to computing system 70. As described above, such inputdevices may be automatically paired to a user depending on a proximityof the user to one or more of the input devices.

Processor 72 may include one or more physical devices configured toexecute one or more instructions. For example, the processor may beconfigured to execute one or more instructions that are part of one ormore applications, services, programs, routines, libraries, objects,components, data structures, or other logical constructs. Suchinstructions may be implemented to perform a task, implement a datatype, transform the state of one or more devices, or otherwise arrive ata desired result.

The processor may include one or more processors that are configured toexecute software instructions. Additionally or alternatively, theprocessor may include one or more hardware or firmware logic machinesconfigured to execute hardware or firmware instructions. Processors ofthe processor may be single core or multicore, and the programs executedthereon may be configured for parallel or distributed processing. Theprocessor may optionally include individual components that aredistributed throughout two or more devices, which may be remotelylocated and/or configured for coordinated processing. One or moreaspects of the processor may be virtualized and executed by remotelyaccessible networked computing devices configured in a cloud computingconfiguration.

Memory 74 may include one or more physical, non-transitory, devicesconfigured to hold data and/or instructions executable by the processorto implement the herein described methods and processes. When suchmethods and processes are implemented, the state of memory 74 may betransformed (e.g., to hold different data).

Memory 74 may include removable media and/or built-in devices. Memory 74may include optical memory devices (e.g., CD, DVD, HD-DVD, Blu-Ray Disc,etc.), semiconductor memory devices (e.g., RAM, EPROM, EEPROM, etc.)and/or magnetic memory devices (e.g., hard disk drive, floppy diskdrive, tape drive, MRAM, etc.), among others. Memory 74 may includedevices with one or more of the following characteristics: volatile,nonvolatile, dynamic, static, read/write, read-only, random access,sequential access, location addressable, file addressable, and contentaddressable. In some embodiments, processor 72 and memory 74 may beintegrated into one or more common devices, such as an applicationspecific integrated circuit or a system on a chip.

FIG. 5 also shows an aspect of the memory in the form of removablecomputer-readable storage media 82, which may be used to store and/ortransfer data and/or instructions executable to implement the hereindescribed methods and processes. Removable computer-readable storagemedia 82 may take the form of CDs, DVDs, HD-DVDs, Blu-Ray Discs,EEPROMs, and/or floppy disks, among others.

It is to be appreciated that memory 74 includes one or more physical,non-transitory devices. In contrast, in some embodiments aspects of theinstructions described herein may be propagated in a transitory fashionby a pure signal (e.g., an electromagnetic signal, an optical signal,etc.) that is not held by a physical device for at least a finiteduration. Furthermore, data and/or other forms of information pertainingto the present disclosure may be propagated by a pure signal.

The terms “module,” “program,” and “engine” may be used to describe anaspect of computing system 70 that is implemented to perform one or moreparticular functions. In some cases, such a module, program, or enginemay be instantiated via processor 72 executing instructions held bymemory 74. It is to be understood that different modules, programs,and/or engines may be instantiated from the same application, service,code block, object, library, routine, API, function, etc. Likewise, thesame module, program, and/or engine may be instantiated by differentapplications, services, code blocks, objects, routines, APIs, functions,etc. The terms “module,” “program,” and “engine” are meant to encompassindividual or groups of executable files, data files, libraries,drivers, scripts, database records, etc.

It is to be appreciated that a “service”, as used herein, may be anapplication program executable across multiple user sessions andavailable to one or more system components, programs, and/or otherservices. In some implementations, a service may run on a serverresponsive to a request from a client.

When included, display subsystem 76 may be used to present a visualrepresentation of data held by memory 74. As the herein describedmethods and processes change the data held by the memory, and thustransform the state of the memory, the state of display subsystem 76 maylikewise be transformed to visually represent changes in the underlyingdata. Display subsystem 76 may include one or more display devicesutilizing virtually any type of technology. Such display devices may becombined with processor 72 and/or memory 74 in a shared enclosure, orsuch display devices may be peripheral display devices.

When included, communication subsystem 78 may be configured tocommunicatively couple computing system 70 with one or more othercomputing devices. Communication subsystem 78 may include wired and/orwireless communication devices compatible with one or more differentcommunication protocols. As nonlimiting examples, the communicationsubsystem may be configured for communication via a wireless telephonenetwork, a wireless local area network, a wired local area network, awireless wide area network, a wired wide area network, etc. In someembodiments, the communication subsystem may allow computing system 70to send and/or receive messages to and/or from other devices via anetwork such as the Internet. Further, communication subsystem may beconfigured for beamforming to locate a position of an input devicewithin an observed scene, as described above.

Sensor subsystem 80 may include one or more sensors configured to senseone or more human subjects, as described above. For example, the sensorsubsystem 80 may comprise one or more image sensors, motion sensors suchas accelerometers, touch pads, touch screens, and/or any other suitablesensors. Therefore, sensor subsystem 80 may be configured to provideobservation information to processor 72, for example. As describedabove, observation information such as image data, motion sensor data,and/or any other suitable sensor data may be used to perform such tasksas determining a position of each of a plurality of joints of one ormore human subjects.

In some embodiments, sensor subsystem 80 may include a depth camera 84(e.g., depth camera 18 of FIG. 1). Depth camera 84 may include left andright cameras of a stereoscopic vision system, for example.Time-resolved images from both cameras may be registered to each otherand combined to yield depth-resolved video.

In other embodiments, depth camera 84 may be a structured light depthcamera configured to project a structured infrared illuminationcomprising numerous, discrete features (e.g., lines or dots). Depthcamera 84 may be configured to image the structured illuminationreflected from a scene onto which the structured illumination isprojected. Based on the spacings between adjacent features in thevarious regions of the imaged scene, a depth image of the scene may beconstructed.

In other embodiments, depth camera 84 may be a time-of-flight cameraconfigured to project a pulsed infrared illumination onto the scene. Thedepth camera may include two cameras configured to detect the pulsedillumination reflected from the scene. Both cameras may include anelectronic shutter synchronized to the pulsed illumination, but theintegration times for the cameras may differ, such that a pixel-resolvedtime-of-flight of the pulsed illumination, from the source to the sceneand then to the cameras, is discernable from the relative amounts oflight received in corresponding pixels of the two cameras.

In some embodiments, sensor subsystem 80 may include a visible lightcamera 86. Virtually any type of digital camera technology may be usedwithout departing from the scope of this disclosure. As a non-limitingexample, visible light camera 86 may include a charge coupled deviceimage sensor. Further, visible light camera 86 may be configured todetect an input device tag to locate a position of an input devicewithin an observed scene, as described above.

It is to be understood that the configurations and/or approachesdescribed herein are exemplary in nature, and that these specificembodiments or examples are not to be considered in a limiting sense,because numerous variations are possible. The specific routines ormethods described herein may represent one or more of any number ofprocessing strategies. As such, various acts illustrated may beperformed in the sequence illustrated, in other sequences, in parallel,or in some cases omitted. Likewise, the order of the above-describedprocesses may be changed.

The subject matter of the present disclosure includes all novel andnonobvious combinations and subcombinations of the various processes,systems and configurations, and other features, functions, acts, and/orproperties disclosed herein, as well as any and all equivalents thereof.

1. A method for automatically pairing an input device to a user, themethod executed by a computing device communicatively coupled to theinput device, the method comprising: receiving an input from an unpairedinput device within an observed scene; calculating a position of theunpaired input device upon receiving the input, the position including adistance and an angle relative to the computing device; detecting one ormore users within the observed scene via a capture device of thecomputing device, the observed scene including the unpaired inputdevice; creating a candidate list of the one or more detected usersdetermined to be within a vicinity of the unpaired input device, thecandidate list including a distance between each user and the unpairedinput device; assigning one detected user on the candidate list to theunpaired input device to initiate pairing, the one user being a nearestuser to the unpaired input device, and once assigned, the unpaired inputdevice being a paired input device.
 2. The method of claim 1, furthercomprising identifying each detected user within the observed scene byidentifying a physical attribute of each detected user and matching thephysical attribute of each detected user to a profile associated witheach detected user.
 3. The method of claim 2, wherein the physicalattribute is detected using three-dimensional imaging, facialrecognition, or biometrics.
 4. The method of claim 1, wherein thereceived input includes at least one of a button press, a joystickmovement, a D-pad movement, a touch event, and a detected motion.
 5. Themethod of claim 4, wherein the unpaired input device includes a motionsensor to sense the detected motion, the motion sensor providing thedetected motion input to the computing device.
 6. The method of claim 1,wherein the unpaired input device includes a tag, and wherein theposition of the unpaired input device is calculated based upon adetected position of the tag.
 7. The method of claim 1, whereincalculating the position of the unpaired input device upon receiving theinput includes a beamforming technique to determine the distance and theangle of the unpaired input device from the computing device.
 8. Themethod of claim 1, wherein the candidate list includes a body portiondistance, wherein the body portion distance is at least one of a handdistance, a geometric center distance, a leg distance, a knee distance,a shoulder distance, and an elbow distance of each detected user asmeasured with respect to the position of the unpaired input device. 9.The method of claim 8, wherein the nearest user is a user on thecandidate list with a strongest correlation to the unpaired inputdevice, wherein one body portion distance for the nearest user has thestrongest correlation to the unpaired input device.
 10. The method ofclaim 1, wherein assigning the nearest user to the unpaired input deviceincludes automatically pairing a profile associated with the nearestuser to the unpaired input device.
 11. The method of claim 1, furthercomprising tracking the nearest user and the paired input device bycorrelating a motion of a body portion of the nearest user to a motionof the paired input device, the motion of the nearest user's bodyportion including the nearest user providing input to the computingdevice via interaction with the paired input device.
 12. The method ofclaim 1, further comprising terminating an association of the nearestuser to the paired input device if input from the paired input device isnot received for a threshold period of time, and if the association isterminated, returning the paired input device to an unpaired state. 13.The method of claim 1, further comprising transferring the paired inputdevice to a second user if a position of the second user has thestrongest correlation to the position of the paired input device, thesecond user being another detected user on the candidate list.
 14. Themethod of claim 1, further comprising pairing more than one input deviceto the user.
 15. The method of claim 1, further comprising switching thepaired input device from a first user to a second user when the seconduser is within a vicinity of the paired input device and the first useris not within the vicinity of the paired input device, wherein the firstuser is a former nearest user and the second user is a current nearestuser.
 16. A memory holding instructions executable by a processor to:receive an input from an unpaired input device within an observed scene;calculate a position of the unpaired input device upon receiving theinput, the position including a distance and an angle from a computingdevice; detect one or more users within the observed scene via a capturedevice of the computing device; create a candidate list of the one ormore detected users determined to be within a vicinity of the unpairedinput device, the candidate list including a distance between each userand the unpaired input device; assign one detected user on the candidatelist to the unpaired input device to initiate pairing, the one userbeing a nearest user to the unpaired input device, and once assigned,the unpaired input device being a paired input device.
 17. The memory ofclaim 16, further comprising instructions executable by a processor toidentify each detected user within the observed scene by identifying aphysical attribute of each detected user and to match the physicalattribute of each detected user to a profile associated with eachdetected user, wherein the physical attribute is detected usingthree-dimensional imaging, facial recognition, or biometrics.
 18. Thememory of claim 16, further comprising instructions executable by aprocessor to track the nearest user and the paired input device bycorrelating a motion of a body portion of the nearest user to a motionof the paired input device, the motion of the nearest user's bodyportion including the nearest user providing input to the computingdevice via interaction with the paired input device.
 19. The memory ofclaim 16, further comprising instructions executable by a processor toterminate an association of the nearest user to the paired input deviceif input from the paired input device is not received for a thresholdperiod of time, and if the association is terminated, returning thepaired input device to an unpaired state.
 20. A method for automaticallypairing an input device to a user, the method executed by a computingdevice communicatively coupled to the input device, the methodcomprising: receiving an input from an unpaired input device within anobserved scene; calculating a position of the unpaired input device uponreceiving the input, the position including a distance and an anglerelative to the computing device; detecting one or more users within theobserved scene via a capture device of the computing device; identifyingeach detected user within the observed scene by identifying a physicalattribute of each detected user and matching the physical attribute ofeach detected user to a profile associated with each detected user;creating a candidate list of the one or more identified users determinedto be within a vicinity of the unpaired input device, the candidate listincluding a right hand distance, a left hand distance, and a geometriccenter distance between each user and the unpaired input device;assigning one detected user on the candidate list to the unpaired inputdevice to initiate pairing, the one user being a nearest user to theunpaired input device, the right hand distance, the left hand distance,or the geometric center distance for the nearest user having a strongestcorrelation to the unpaired input device, and once assigned, theunpaired input device being a paired input device; tracking the nearestuser and the paired input device by correlating a motion of the nearestuser's right hand or left hand to a motion of the paired input device,the motion of the nearest user's right hand or left hand including thenearest user providing input to the computing device via interactionwith the paired input device; terminating an association of the nearestuser to the paired input device if input from the paired input device isnot received for a threshold period of time, and if the association isterminated, returning the paired input device to an unpaired state; andtransferring the paired input device to a second user if a position ofthe second user has the strongest correlation to the position of thepaired input device, the second user being another detected user on thecandidate list.